-
-
Notifications
You must be signed in to change notification settings - Fork 151
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add ability to execute console commands from file #96
Conversation
c272b8c
to
8f8c6f1
Compare
I like this change a lot |
Sorry i am newbie... how to do this change ? |
If you're a noobie you'll need to wait for this PR to be approved and then release with the change to be made. If you're willing to learn how to compile software from source you can pull my branch and build your own .dlls |
Thank you so much for your answer, and for your work generaly. |
Without this change you need to find game profile directory which should be [SystemSettings]
r.WaterSurfaceReflections=0 When this change lands you'd create |
8f8c6f1
to
21330ea
Compare
Should look into using UEngine::exec now, it is possibly more stable, though would have to examine its stability across games as it is new It also has access to the "exec" functions that are completely unseen by the console manager (I think anyways? I'd have to double check whether this can still run commands like "fly") |
Yes it's part of the scanning process. It can be optimized more. |
I'll try then. In case loading list of commands takes a long time we can revert to current implementation. For some games I needed 30 or so parameters. I hope it does not need to scan like this for each one. |
No, it only needs to do it once |
@praydog I've just noticed that Anyhow new version of this patch using |
Certain game profiles need CVars from outside the scope provided by UEVR. Editing engine.ini makes profile sharing more complicated. This changeset adds ability to execute commands from `user_script.txt` located inside game profile folder. This allows flexible customization bundled in profiles that need it. Syntax and effects are the same as commands were entered in native console. Namely one command per line, space separated arguments. Comments are supported in form of whole line comments starting with '#' or ';'. Additionally inline comments are supported in form of `command param # comment` Example is Abzu where addding snippet `r.WaterSurfaceReflections 0` to `user_script.txt` disables distracting visual effects.
21330ea
to
6efe0d3
Compare
Certain game profiles need CVars from outside the scope provided by UEVR. Editing engine.ini makes profile sharing more complicated.
This changeset adds ability to execute commands from
user_script.txt
located inside game profile folder.Syntax and effects are the same as commands were entered in console. Namely one command per line, space separated arguments.
This allows flexible customization bundled in profiles that need it.
Example use case is Abzu where adding snippet
r.WaterSurfaceReflections 0
touser_script.txt
disables distracting visual effects.EDIT: Revised version uses
UEngine::Exec()
which allows any command that would work in UE native console.It also supports comments so following syntax is correct: